CloudCockpit Team | Published July 21, 2026
A scoped self-service portal does not replace the CSP customer relationship, because Microsoft already requires the partner to be the customer's only point of contact for support and subscription changes. What changes with a portal is not who owns the relationship; it is which requests still need a human. Below is the distinction that matters: routine work versus relational work, and why only one of them needs to move.
CSP customers cannot open a support request directly with Microsoft. Microsoft's own documentation is explicit: "CSP customers can't create support requests themselves. They must contact you for support." Direct Bill partners own that relationship end to end, and Indirect Resellers work through their Distributor for the same responsibility.
That design choice is why routine requests and relational conversations land in the same inbox today, with nothing filtering them apart before they reach your team. A typical week for a CSP support team includes:
None of these require a relationship decision. All of them currently require a person to handle them.
No, a self-service portal does not have to expose everything or remove the partner from the sale process. Microsoft's own guidance to partners on building this kind of portal is explicit that it does not mean customers purchase directly through Microsoft Admin Center. It is guidance for the partner to build a portal, under the partner's own brand, on the partner's own terms.
A CSP decides what to expose and what to keep human. A typical scope looks like this:
Nothing in those first two rows requires exposing the third.
CloudCockpit Note: the reflex to reject self-service because "our customers value the relationship" usually conflates two different things. Customers rarely value having to email someone to check their own renewal date. They value the conversation about what to do next. A scoped portal removes the first and protects time for the second.
Yes, through the Support Services designation, which measures partner support performance using a metric called Case Rate. Case Rate is calculated as CSP Case Volume (TTM) divided by CSP plus ACR Billed Revenue (TTM), multiplied by 1,000,000, and a lower Case Rate scores better.
Every seat change, invoice question, or renewal lookup that a customer resolves through a portal is a support case that never gets opened, which lowers Case Rate without reducing the actual relationship work your team does.
This designation is available to Direct Bill and Distributor CSP partners specifically. Indirect Resellers do not enroll in it directly and depend on their Distributor's standing instead.
Scoping self-service correctly is an operational problem before it is a product decision, because a CSP is usually managing agreement data, price lists, and billing across dozens or hundreds of customer tenants at once. Doing that scoping by hand, tenant by tenant, is exactly the kind of routine work this article argues should not consume a support team's time either.
Platforms built specifically for CSP automation exist to solve that layer. A platform like CloudCockpit, for example, centralizes:
CloudCockpit has run this model since 2016, across more than 40 countries, managing over €170M in cloud commerce annually for Microsoft CSP partners specifically.
Microsoft's CSP program already makes the partner the customer's only point of contact, which is exactly why routine requests and relational conversations end up mixed together in the same queue. A self-service portal scoped to routine tasks, seat changes, invoice visibility, renewal status, does not hand the relationship to a webshop. It removes the noise around the relationship so the conversations that actually require a person, pricing, packaging, renewal strategy, get the attention they need. For Direct Bill and Distributor partners, it also improves the Case Rate metric Microsoft uses to evaluate support performance.